An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hello, We are reaching out asking for help reaching someone who can investigate an unresolved App Review situation and unanswered support requests. Across our original submission and resubmission, we have been unable to deliver important iOS updates for 1 month. During this period, an SMS-pumping incident forced us to suspend phone-number registration. Additional client-side protections are ready, but we cannot get them to App Store users while the current submission remains unresolved. Brrro is a startup that reached number one on the Greek and Cypriot App Stores, including Greece’s overall chart and Social Networking category. We have a growing user base, ongoing press interest, and users waiting for fixes we have already completed. This delay is materially affecting our ability to operate and has forced us to postpone our marketing campaign. App details: App: Brrro – Secure Messenger Apple ID: 6756784288 The timeline and outstanding issues are as follows: Our original update was rejected after more than two weeks of waiting, under Guideline 2.3.1(a). The rejection cited a game accessed through a hidden entrance, alongside the app’s decoy PIN, alternate icons, and user-triggered data-deletion features. It also included an extended-review warning. We addressed the game’s discoverability by making it accessible through a clearly labeled Games entry in Settings instead of the triple-tap entrance. We also explained the purpose and discoverability of the user-configured privacy and security features. The earlier submission was withdrawn, and version 4.0.1 was submitted on 24 September. It entered In Review on 25 September and remains there as of 5 October. We submitted an expedited-review request and contacted support, including follow-ups. We have not received a substantive response explaining the outstanding concern or what action is required from us. During this delay, an SMS-pumping attack generated thousands of dollars in verification charges. We suspended phone-number registration and prepared additional client-side verification protections. These are not included in the 4.0.1 build currently under review; We need assistance with both the unresolved review and the lack of communication. Could an Apple representative please help confirm: Whether our case remains open and which team is handling it. Whether the current submission remains subject to extended review. Whether any specific feature, documentation, or reviewer-access issue requires action from us. How we can arrange direct contact with App Review and receive a substantive next step. Whether any unresolved concern could also affect subsequent security updates, and what we need to do to resolve it. If a feature needs changing, we are available to act immediately once the requirement is clearly explained. We can also provide reviewer access, a walkthrough, submission screenshots, and incident evidence through a private support channel. We need a concrete response so that we can deliver fixes to our users and plan the operation of our business. This is hurting us as a startup and might even drive us out of business Brrro Team

Hey guys i think am not the only one experiencing this delays from Apple review team , it has been like that now +10 days , does anyone know, what is going on??

Hello Apple App Review Team, I’m reaching out to request an update on the review status of my app, LetsGo Cayman.

Hi everyone, We resubmitted a new banking app on September 30 after a 2.1(a) rejection (the reviewer didn't complete the OTP step; we clarified the steps in our reply and review notes). It has been in "Waiting for Review" since then. Apple ID: 6779648622 Expedited review requested Oct 1 Support case opened Oct 2 (Case ID 102983863768) Updated Program License Agreement accepted Oct 6 The client's launch has already been postponed once, to October 14, because of the delay. Is anyone else seeing similar wait times right now, or is there anything else we should check on our side? Thanks!

Hi App Review team, Our new iOS app was rejected on September 30, 2026 under Guideline 2.1(a) related to demo account access. We replied in App Store Connect with clarifying questions that same day and have not received a response in nearly a week. We also opened Case ID 102983881736 on Friday with no reply yet. The reviewer ran into two separate sign-in issues: Sign in with Apple: Our app is a companion app for an existing web platform, so it currently only allows sign in for accounts already set up on our website. The reviewer's Apple ID showed the expected "Please sign in on the web app to continue" message. Since Sign in with Apple uses the reviewer's own Apple ID, we can't provide standalone credentials for it. Google: Our Google demo account was hit with a Google "Verify it's you" security challenge. That prompt comes from Google, not our app. We can't reliably provide Google or Microsoft demo credentials, because we can't control when those providers trigger security checks during review. To solve both issues, we've built invite code support into the sign-in flow. When a user successfully signs in with Google, Microsoft, or Apple and no account exists for that email in our system, the app now prompts for an invite code instead of showing the "Please sign in on the web app to continue" message. For review, the reviewer would sign in with their own account and enter an invite code from our App Review Information notes, which links their OAuth sign-in to a fully seeded demo account. Before resubmitting, we need answers to two questions: Is this invite code approach acceptable for review? Does the reviewer need to test all three sign-in methods (Google, Microsoft, and Apple), or is one enough? This tells us whether to provide one invite code or a separate code for each method. We'd like to confirm this before resubmitting so the next review goes smoothly, but our launch is on hold until we hear back, so a reply soon would be greatly appreciated. All other fixes are complete. Once we have an answer, we will add the invite code(s) to our App Review Information notes and resubmit with a new build right away. Thank you.

Hello, Our app Virtual Pro Association has been stuck in “Waiting for Review” since September 28, 2026 at 21:46. We requested an Expedited App Review, and Apple confirmed that the request was accepted with the message: “We’ll expedite review for Virtual Pro Association.” Despite this, almost 6 days have passed and the submission has still not moved to “In Review.” We have also contacted App Review Support regarding the review status and are currently waiting for a response. App: Virtual Pro Association Version: 1.0 Build: 72 Apple ID: 6809065140 There are no messages, rejections, or actions required in App Store Connect. Has anyone experienced a similar delay recently, especially after an expedited review was granted? Is there anything else we should do, or should we simply keep waiting? Thank you.

I have an App Store version stuck In Review. I need to cancel / remove it from review so I can submit a newer build. I contacted Apple Developer Support. They said they cannot manually remove the app from review and that I have to cancel it myself. I have tried everything on my side: App Store Connect web UI → Remove this version from review / Cancel Submission App Store Connect on iPhone App Store Connect API (canceled: true on the review submission, and removing the submission item) Every attempt fails. In the UI I get errors like “An error has occurred. Try again later” / “Your changes could not be saved. Try again later.” Via the API I get HTTP 409 STATE_ERROR.ENTITY_STATE_INVALID (“Resource cannot be canceled at the moment, please try again later” / “Cannot remove item because of state of reviewSubmission”). The version stays In Review. I’ve reproduced this in Chrome and Safari, and on the phone app, plus the API so it doesn’t seem like a browser-only issue. Has anyone gotten past this when Support says you must cancel it yourself but Connect won’t let you? Any workaround, or is waiting for Apple the only option?

Submitted my third brand new on 15 Sep. Three weeks later it's still sitting in "Waiting for Review". Sent an expedite request on the 27th, heard nothing. By now the build in review is already pretty outdated, and I might have to wait another two weeks after sending the newer version. But I don't want to pull it and end up at the back of the queue. Anyone else seeing waits this long right now? And if it gets approved, does an update usually go through faster, or should I swap the build while I'm waiting?

App Review's automated message (3.0.0 Business: Preamble) arrived on 1 October at 10:14 AM CDT. It asked us to confirm the price of a non-consumable in-app purchase. We confirmed the price in the same thread at 10:21 AM CDT, and wrote again on 5 October at 10:00 AM CDT. As of 6 October it has been nearly 5 days since our answer, with no reply in the thread. Developer Support (case 102978876606) estimated 48 hours on 1 October. The submission still shows "Unresolved Issues" and the app version shows "Rejected". What we have already done: replied in the thread; confirmed the price in writing; left the build and all four in-app purchase items unchanged and "Ready for Review"; opened the Developer Support case above. Two questions: Has anyone gone through this exact message, and how did it end (a reply, a status change, a resubmission)? How long did it take? Are we missing a step besides replying to the question, such as resubmitting, or changing something on the in-app purchase page? App ID 6808337831. Thank you.

Hi everyone, A week and a half after we started the validation process for our app, we’re still stuck with just one response every 24 to 48 hours, and now there are only three days left before the game’s release. The testers aren’t replying, even though I reply politely and send videos to show them how to do it. They test the wrong version, no send of video problem, etc. I don’t know if I’ve ever experienced anything quite as stressful. Three years’ work is at risk because the testers aren’t replying or aren’t reading my messages. How can I speed up the approval process? Or how can I get in direct contact with the people responsible for review ? I’m willing to pay if necessary ! The game was tested during 3 month no problem, this last version works fine on my end, on iPhone and iPad, yet I keep getting the same non-constructive response over and over. I sended video that prouve that. What’s wrong with this review system? Can anyone help me? I’m desperate – our game has been announced and is due to be released on 8 October.... Best Regards Pierre Proudhon

Hello, Our app NUTRIFIT FEMME has been in Waiting for Review for approximately one week. There are no rejection messages or requests for additional information in App Store Connect. Could someone from Apple please confirm whether the submission is processing normally or whether any action is required from our side? Thank you.

My first iOS app, Yug Purushottam, was originally submitted to App Review on September 27, 2026 at 2:56 PM Pacific Daylight Time. Apple subsequently returned the submission under Guideline 2.1 – Information Needed – New App Submission and requested additional information because the developer account has limited App Review history. I provided everything requested, including: A screen recording captured on a physical iPhone showing the app launch and normal user flow Registration and login flow Account deletion and revocation flow Detailed information about the app’s purpose, target audience, external services and regional behavior Updated App Review Information and Notes The submission was then successfully resubmitted on Friday, October 2 at 6:25 AM, and App Store Connect has remained at “Waiting for Review” since then. It has still not moved to “In Review.” I have also already submitted an Expedited App Review Request and contacted Apple through the App Review Status support channel, but so far there has been no progress. The app is complete, has been tested on a physical device, and all information requested by App Review has already been supplied. Has anyone recently experienced a similar delay with a first App Store submission, particularly after a Guideline 2.1 information request? Is there any further escalation route available when a submission remains in “Waiting for Review” despite an Expedited App Review Request and an App Review Status support case? Any recent experience with how long this situation eventually took to resolve would be very helpful.

To learn how to prevent copycat and impersonation rejections, visit 4.1 - Preventing copycat and impersonation rejections on App Review Help.

To learn best practices for before and after submitting your app for review, visit App Review Help.

To learn about supporting your app on multiple devices, visit Test your app on compatible devices on App Review Help.

To learn how to best prepare your app for an efficient review, visit Test your app on compatible devices, Configure In-App Purchases for review in the sandbox, and Provide information for a complete review on App Review Help.

Hi everyone, I'd like to raise a concern about the transparency and fairness of Guideline 4.3 reviews. A rejection that says an app duplicates existing functionality or is indistinguishable from widely available apps should explain what specifically led to that conclusion. General categories, followed by an instruction to make substantial improvements, do not give developers an actionable path forward. Which functionality is the problem? Which aspects need to change? What standard would satisfy the reviewer? Without concrete examples or a clear threshold, the assessment feels highly subjective. Developers can spend significant time building a product and still be left guessing what would make it acceptable. In my view, independently developed apps should be able to compete in existing categories. Products naturally share basic functionality when they solve the same problem. Competition can come from a better workflow, a clearer interface, privacy, pricing, accessibility or serving a different audience. It should not require every developer to invent an entirely new category. If similar functionality alone is enough to reject a new entrant, that risks protecting established apps from competition. That feels unfair to independent developers and limits users' choice. The first app to enter a category should not effectively own that category. I support preventing copied apps, repetitive submissions and low-quality template spam. But there needs to be a clear, consistently applied distinction between spam and legitimate alternatives. A developer should be able to understand the reasoning behind a rejection and respond to specific concerns. Could Apple clarify: What specific evidence should reviewers provide when rejecting an app under 4.3? How is ordinary competition within a category distinguished from unacceptable duplication? What concrete criteria establish sufficient differentiation, and how are they applied consistently? When 4.2.6 is mentioned alongside 4.3, can the reviewer explain whether there is an actual template-related finding and what supports it? What is the best process for obtaining an actionable explanation when the rejection only lists general possibilities? Asking developers to make substantial changes is reasonable when the issue is clearly identified. Asking them to guess at an unstated standard is not. Clear reasons and consistent criteria would help developers improve their products while giving new entrants a fair opportunity to compete. Has anyone successfully obtained specific, useful clarification in this situation?

I have a macOS app that has be in “waiting for review” status since September 27 and the same app’s iOS build has been waiting since September 30th. Is this normal wait time for an app to enter the review process?

Hello everyone, I submitted my app for review on October 2nd, and it has been in the "Waiting for Review" state since then. Has anyone else experienced similar delays recently? Any advice on whether I should just wait or reach out to support would be greatly appreciated. Thanks!

Xcode version 26.6 (17F113) MyOwnKeyboard-PAD app looks OK using simulator iPad Air 11-inch(M4). It automatically reformats to all orientations using only left and right landscape selected in General, Deployment Info. The submitted app 1.9 (4) had the portrait checked which was an error. I tried to update to version to 1.10 without portrait and upside down, but Validation states it must have all orientations needed. I tried setting all orientations and the simulator cuts off the sides. I am using a new mini M4 with Tahoe 26.6.2 Converted from an older developer mini using Migration Assistant. After conversion Xcode could not find xcspace files and apps locked up. I had to create new apps with different bundles which got conflicted in AppConnects causing rejects. When new versions are submitted, old versions cannot be removed because of submission states. Causing similar binaries, design and scam. I got trapped in the process! I have replied to AppConnect ref. binaries, design and scam. I hope someone can straighten this mess out. The good new is the free MyOwnKeyboard-PHONE analytics look OK with 4,000 impressions and 38 downloads and 172 product page reviews. It's a start! Thank you. Charlie Coupe Designer/Coder 2026sep16